Artifact: Stakeholder Requests

Stakeholder Requests	This artifact contains any type of requests a stakeholder (customer, end user, marketing person, and so on) might have on the system to be developed. It may also contain references to any type of external sources to which the system must comply.
Worker:	System Analyst
Template:	Microsoft Word Template HTML Template
More Information:	Work Guidelines: Interviews Work Guidelines: Requirement Workshop Concepts: Change Request Management Checkpoints: Stakeholder Requests
Purpose Brief Outline Timing Responsibility Annotated Outline (hyperlinks into HTML template in a new window)

Input to Activities: Capture a Common Business Vocabulary Capture a Common Vocabulary Detail a Business Use Case Detail a Use Case Develop Vision Find Actors and Use Cases Find Business Actors and Use Cases Manage Beta Test Manage Dependencies Model the User Interface

Output from Activities: Elicit Stakeholder Requests

Purpose

The purpose of this artifact is to capture all requests made on the project, as well as how these requests have been addressed. Although the system analyst is responsible for this artifact, many people will contribute to it: marketing people, end users, customersùanyone who is considered to be a stakeholder to the result of the project. This information may be collected in a document or automated tool and appropriate requests should be tracked and reported on following an approved Change Request Management (CRM) process.

Examples of sources for the Stakeholder Requests are:

• Results of stakeholder interviews (see outline below for a sample script template)
• Results from requirements elicitations sessions and workshops
• Change Request (CR)
• Statement of work
• Request for proposal
• Mission statement
• Problem statement
• Business rules
• Laws and regulations
• Legacy systems
• Business models

Brief Outline

Following is a sample outline for a Generic Interview script, one of the methods which may be used for eliciting stakeholder requests.  Select the links below to view sample questions which may be asked to elicit the stakeholder request information. (hyperlinks into HTML template in a new window)

1.       Introduction         

    1.1     Purpose     

    1.2     Scope     

    1.3     Definitions, Acronyms and Abbreviations     

    1.4     References     

    1.5     Overview     

2.       Establish Stakeholder or User Profile

3.       Assessing the Problem         

4.       Understanding the User Environment

5.       Recap for Understanding

6.       AnalystÆs Inputs on StakeholderÆs Problem (validate or invalidate assumptions) 

7.       Assessing Your Solution (if applicable)     

8.       Assessing the Opportunity  

9.       Assessing Reliability, Performance and Support Needs

10.      Wrap-Up               

11.      AnalystÆs Summary         

Timing

Stakeholder Requests are mainly collected during the inception and elaboration phases, however they should continue to be collected throughout the project lifecycle for planning enhancements and updates to the product.  A change request tracking tool is useful for collecting and prioritizing these requests.

Responsibility

A system analyst is responsible for the integrity of the Stakeholder Requests artifact, ensuring that:

• All stakeholders have been given the opportunity to add requests.
• All items in this artifact are taken into consideration when developing detailed requirements in the use-case model and the supplementary specifications.

Copyright  ⌐ 1987 - 2000 Rational Software Corporation

Rational Unified Process